🦋 Changeset detected

Latest commit: a7c1cc0

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

I'd like to understand what problem this is actually solving for you before considering whether this feature should be added. The vite plugin already loads your existing vite config when creating the compiler - see here - so anything you want to override could instead just be done in your own vite config, instead of by the plugin.

I want to actually "override" the config so have a separate config for running VE transforms, not just inheriting the primary config.

My usecase is kinda tricky. The Solid Vite plugin emits browser-only code if it's not an SSR build, which breaks VE evaluator to break. However since VE Vite plugin just takes my Vite config and runs transform with it, it's impossible to prevent Solid Vite plugin from emitting those code.

While this specific usecase can be fixed by filtering out the Solid Vite plugin (like what we're already doing with the Remix plugin) issues like this will always come up as the target environment between Vite and VE Vite plugin will be always different (unless it's a SSR build) Therefore having an escape hatch will be valuable enough to let users workaround their issues.